- 
                Notifications
    You must be signed in to change notification settings 
- Fork 313
feat: update several path for image.tag #793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master-annotation-based
Are you sure you want to change the base?
feat: update several path for image.tag #793
Conversation
| Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@             Coverage Diff             @@
##           master     #793       +/-   ##
===========================================
+ Coverage   70.85%   82.70%   +11.84%     
===========================================
  Files          45       22       -23     
  Lines        5178     1954     -3224     
===========================================
- Hits         3669     1616     -2053     
+ Misses       1344      282     -1062     
+ Partials      165       56      -109     ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
 | 
| @Tchoupinax thanks for proposing it. I'll look into it. | 
| Hello @chengfang, | 
| Some other places assume that image.name and image.spec represent single-path value, and we should think about if it makes sense for those places to also take multi-path values. For instance, argocd-image-updater/pkg/argocd/update.go Line 449 in 4f21ade 
 argocd-image-updater/pkg/argocd/update.go Line 473 in 4f21ade 
 | 
Signed-off-by: Tchoupinax <[email protected]>
Signed-off-by: Tchoupinax <[email protected]>
Signed-off-by: Tchoupinax <[email protected]>
| I will give a look but maybe I need help on your last point (checking if having two paths is OK everywhere) | 
Hello folks!
I made this improvement to handle a case we have at work. Let's explain it.
In the current case, we provide a path for the image tag with the annotation
.helm.image-tag. It says where to update the tag for this argoCD application.Now, I have one ArgoCD application with two deployements, different with a suffix. Let's call them
aandb. So my helm-chart values are prefixed by the alias of each app.I want to update both at the same time, the lifecycle is identical. This merge request allows to do it, by adding several paths as value separated by a comma. Then, I can provide
xxxx.helm.image-tag=a.image.tag,b.image.tagA unit test has been added about tag and name and moreover, I handled every space to ensure it won't have any bug for a mistype.
Finally, I build the customized image and tested, all is OK for me.
I hope all is clear!
Thank you for your work, I love this project.
Cheers!